The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!
From the Wiki University
What evidence can you provide to prove your understanding of each of the following citeria?
Plan the test effort and develop test strategy for an application software
|
|
Analyse the functionalities of an application software from the system design document and create a test strategy for a new telecommunications product line Completed |
Evidence:
|
Produce the steps in developing the test strategy and the attributes of each step according to enterprise policy Completed |
Evidence:
|
Produce a test strategy for evaluating the suitability of the application software for integration into the telecommunications network Completed |
Evidence:
|
Analyse the test strategy and identify the types of risks that would hinder the test performance or reality Completed |
Evidence:
|
Plan test strategy for the regime
|
|
Produce the phases of a test cycle for a test regime according to the system design document Completed |
Evidence:
|
Assess a range of tests required to evaluate the performance and functionality of the application software and determine the tests required to suit the test regime Completed |
Evidence:
|
Evaluate features of testing tool and debuggers and select an appropriate tool to test the software application and detect faults Completed |
Evidence:
|
Evaluate the elements of a test plan that would cover the testing functionality of the application software Completed |
Evidence:
|
Design a test plan and produce test reviews
|
|
Determine the forecast time, effort and cost for low and medium intensity projects to perform testing Completed |
Evidence:
|
Develop a test case or test scenario with prerequisite states based on requirements to generate expected test results for the test plan Completed |
Evidence:
|
Produce a test plan for specific phases based on the requirements of the project specifications for the application software Completed |
Evidence:
|
Produce test reporting associated with particular test phases within the test plan Completed |
Evidence:
|
Analyse test reports and evaluate the impact of the test plan on the testing environment Completed |
Evidence:
|
Manage the progress of the test plan to minimise the risks associated with testing and ensure test compliance with test requirements Completed |
Evidence:
|
Report any detected defects to the product evaluation personnel and prepare a strategy to manage the defects Completed |
Evidence:
|
Manage test traceability
|
|
Create a traceability matrix to correlate the relationship between marketing requirements and detailed requirements of the software product to the matching parts of design, test plan and test cases Completed |
Evidence:
|
Analyse the testing metrics produced by the test tool to manage the tracking of defects and plan process improvements based on the metrics Completed |
Evidence:
|
Produce an evaluation report from the traceability matrix to manage the defects or failures from the test plan Completed |
Evidence:
|